fix: security fix for cross-site scripting (xss)#611
Open
mikegioia-ss wants to merge 2 commits intojquery-form:masterfrom
Open
fix: security fix for cross-site scripting (xss)#611mikegioia-ss wants to merge 2 commits intojquery-form:masterfrom
mikegioia-ss wants to merge 2 commits intojquery-form:masterfrom
Conversation
… and package lock file.
Author
|
Greetings team -- this is an updated version of the wonderful fix from #586 I included a dist file, an updated version to 4.3.1, and everything I believe is needed for a proper update. Please let me know if there is anything else I can do to help. |
sbesson
pushed a commit
to ome/omero-web
that referenced
this pull request
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The form library suffered of a XSS issue, which was caused by 2 minor issues inside the code, which made possible the usage of eval on unsanitized values (inside the "override" of parseJSON) and html parsing on a unsanitized AJAX response.
The 2 issues have been fixed in the following way: